Object processing system using an object model

ABSTRACT

Several tools are included in an object processing system that also includes a common object model containing a data structure and an administrative program for the data structure. The tools have read access and optionally also write access to partial areas of the data structure via the administrative program. The partial areas can be different from one another and can contain mutually corresponding information. The administrative program optionally updates the other partial areas by compulsion, during write access approaches by a tool.

[0001] The present invention relates to an object processing system having an object model and at least one basic tool and a supplementary tool,

[0002] where the object model has a data structure and an administrative program for the data structure,

[0003] where the data structure can be accessed by the tools using the administrative program,

[0004] where the data structure comprises a control program which can be executed by a process control unit and can be taken as a basis for the process control unit to control and/or monitor a technical installation using at least one input/output unit,

[0005] where the data structure contains information about variables used by the process control unit when executing the control program, the storage location of said variables in the process control unit and possibly their links to one another,

[0006] where the basic tool has read access to an associated subregion of the data structure,

[0007] where the supplementary tool has read and write access to an associated subregion of the data structure,

[0008] where the subregions differ from one another at least in part and contain information items which correspond to one another.

[0009] Object processing systems are known generally. They normally involve the individual tools, independently of one another, accessing models which have a proprietary association with the respective tools. This applies equally to read and write access operations.

[0010] On account of the access operations to the individual models being independent of one another, the information items corresponding to one another in the models can be or can become inconsistent with respect to one another. In order to achieve consistency of the information nonetheless, the prior art involves complex implementation of checking passes and mapping mechanisms. Nevertheless, consistency is not always guaranteed for the information items corresponding to one another in the models, or data are lost. The latter is true particularly if the same object is manipulated by a plurality of tools. It may also be necessary for data to be input a plurality of times if the corresponding mapping mechanisms are not available. In addition, the mapping mechanisms need to be programmed.

[0011] The object of the present invention is to provide an object processing system of the type mentioned initially in which consistent data management is easily ensured.

[0012] The object is achieved by virtue of the object model being in the form of a common object model and by virtue of the administrative program being designed such that write access to the data structure by the supplementary tool involves that subregion of the data structure which cannot be read by the supplementary tool being mandatorily updated at the same time if appropriate.

[0013] The basic tool is normally a user interface display tool or an execution tool for the control program. Correspondingly, the supplementary tool is normally a user interface creation tool or a control program creation tool.

[0014] Other combinations of tools are also possible, however. In particular, the object processing system can comprise all four of the aforementioned tools. In all cases, however, write access to the data structure by one of the tools always involves mandatory updating of all those subregions of the data structure which cannot be read by this tool.

[0015] If the data structure has a common region to which at least two tools have read access, the data structure is utilized particularly efficiently. In addition, the complexity of updating is reduced.

[0016] If the data structure contains a full information record for each tool which has access to the data structure, it can be used fully by any corresponding tool.

[0017] If a computer having such an object processing system is in the form of a process control unit, it is always ensured that the data called from the data structure by the tools reflect the control program which is to be executed by the process control unit.

[0018] If the computer is in the form of a computer with Internet capability and the tools can be called via the Internet, it is possible to call the tools from other computers. This naturally does not apply to the execution tool for the control program, which must always be executed by the process control unit itself.

[0019] Other advantages and details can be found in the description below of an exemplary embodiment in conjunction with the drawings, which comprise a basic illustration in which

[0020]FIG. 1 shows an object processing system,

[0021]FIG. 2 shows a flowchart, and

[0022]FIG. 3 shows a computer network.

[0023] In line with FIG. 1, an object processing system 1 has four tools 2 to 5. These are an execution tool 2 for a control program SP, a user interface display tool 3, a control program creation tool 4 and a user interface creation tool 5. Within the context of the present invention, the execution tool 2 and the user interface display tool 3 are basic tools, and the control program creation tool 4 and the user interface creation tool 5 are supplementary tools.

[0024] The tools 2 to 5 can access a data structure 6. In this case, access is effected using an administrative program 7 for the data structure 6. The data structure 6 and the administrative program 7 together form an object model 8 which is common to all the tools 2 to 5.

[0025] For each of the tools 2 to 5, the data structure 6 contains a full information record. The information records are stored in subregions 9 to 12 of the data structure 6. In this case, the information record for the execution tool 2 forms the control program SP. Each of the tools 2 to 5 has read access to its associated subregion 9 to 12. The control program creation tool 4 and the user interface creation tool 5 also have write access to their associated subregions 11, 12.

[0026] As can be seen, the subregions 9 to 12 overlap but are not identical to one another. The subregions 9 to 12 thus differ from one another in part. However, the data structure 6 also has common regions 13 to 19 to which at least two tools 2 to 5 have read access.

[0027] The subregions 9 to 12 contain information items which correspond to one another. By way of example, they contain information about variables used by a process control unit 20 when executing the control program SP, the storage location of said variables in the process control unit 20 and possibly their links to one another. These information items need to be consistent with one another.

[0028] Hence, when the control program creation tool 4 or the user interface creation tool 5 effect write access to their associated subregions 11, 12, the other subregions 9, 10, 12 or 9 to 11 also need to be updated in order to ensure consistent data management. This task is performed by the administrative program 7. This program is designed such that, upon write access, it checks whether any updating is required and mandatorily performs this updating if appropriate.

[0029] In line with FIG. 2, the administrative program 7 detects access requests in a step 21 and performs them in a step 22. In a step 23, the administrative program 7 then checks whether the access was read access. If so, the next access request is awaited. Otherwise, a step 24 is used to check whether a common region 13 to 19 (common to all tools 2 to 5) has been accessed. If so, the next access request is awaited. Otherwise, a step 25 is used to check whether the information written was singular and the other subregions 9, 10, 12 or 9 to 11 thus contain no corresponding information. If so, the next access request is awaited. Otherwise, the administrative program 7 updates the subregions 9, 10, 12 or 9 to 11, if required, in a step 26.

[0030] In the simplest case, this involves pure copying. However, it is also possible for functional dependencies to exist. In this regard, the administrative program 7 has access to meta-information about the object model 8 so that the subregions 9 to 12 can be kept consistent in this case as well.

[0031] In line with FIG. 3, the object processing system 1 is stored in the process control unit 20. The computer 20 storing it is thus in the form of a process control unit 20. The process control unit 20 can execute the control program SP. This involves the process control unit 20 reading in process states from an industrial technical installation 28 via input units 27. In addition, it uses output units 29 to output control commands to the industrial technical installation 28. The process control unit 20 thus monitors the industrial technical installation 28 using the input units 27 and controls it using the output units 29.

[0032] Execution of the control program SP, that is to say implementation of the execution tool 2, needs trivially—to occur in the process control unit 20 itself. By contrast, execution of the other tools 3 to 5, that is to say of the user interface display tool 3, of the control program creation tool 4 and of the user interface creation tool 5, can also occur in other computers 30 to 32. To this end, the process control unit 20 is or can be connected to these computers 30 to 32 via the Internet 33. The process control unit 20 is thus in the form of a computer 20 with Internet capability. The other tools 3 to 5 can therefore be called via the Internet 33, which allows remote programming and remote control of the process control unit 20.

[0033] The object model 8 is a unit. Preferably, it is therefore stored on a single computer 20, in this case on the process control unit 20. If suitable mechanisms ensure consistency, it can also be stored in distributed form, however. Preferably, as described, the tools 2 to 5 are also stored on the process control unit 20. This is also not absolutely necessary, however. 

1. An object processing system having an object model (8) and at least one basic tool (2, 3) and a supplementary tool (4, 5), where the object model (8) is in the form of a common object model (8) which has a data structure (6) and an administrative program (7) for the data structure (6), where the data structure (6) can be accessed by the tools (2-5) using the administrative program (7), where the data structure (6) comprises a control program (SP) which can be executed by a process control unit (20) and can be taken as a basis for the process control unit (20) to control and/or monitor a technical installation (28) using at least one input/output unit (27, 29), where the data structure (6) contains information about variables used by the process control unit (20) when executing the control program (SP), the storage location of said variables in the process control unit (20) and possibly their links to one another, where the basic tool (2, 3) has read access to an associated subregion (9, 10) of the data structure (6), where the supplementary tool (4, 5) has read and write access to an associated subregion (11, 12) of the data structure (6), where the subregions (9-12) differ from one another at least in part and contain information items which correspond to one another, where the administrative program (7) is designed such that write access to the data structure (6) by the supplementary tool (4, 5) involves that subregion (9, 10, 12 or 9-11) of the data structure (6) which cannot be read by the supplementary tool (4, 5) being mandatorily updated at the same time if appropriate.
 2. The object processing system as claimed in claim 1, characterized in that the basic tool (2, 3) is a user interface display tool (3).
 3. The object processing system as claimed in claim 2, characterized in that the supplementary tool (4, 5) is a user interface creation tool (5).
 4. The object processing system as claimed in claim 1, characterized in that the basic tool (2, 3) is an execution tool (2) for the control program.
 5. The object processing system as claimed in claim 4, characterized in that the supplementary tool (4, 5) is a control program creation tool (4).
 6. The object processing system as claimed in one of the above claims, characterized in that the data structure (6) has a common region (13-19) to which at least two tools (2-5) have read access.
 7. The object processing system as claimed in one of the above claims, characterized in that the data structure (6) contains a full information record for each tool (2-5) which has access to the data structure (6).
 8. A computer having an object processing system (1) as claimed in one of the above claims.
 9. The computer as claimed in claim 8, characterized in that it is in the form of a process control unit (20).
 10. The computer as claimed in claim 8 or 9, characterized in that it is in the form of a computer (20) with Internet capability and in that the tools (3-5) can be called via the Internet (30). 